Avalanche Bridge

Ethereum to C-Chain, done carefully

Avalanche Bridge moves supported Ethereum assets to Avalanche C-Chain and back, using locked collateral, minted representations, and your own wallet signatures.

Preview

Preview only
Ethereum tokenEthereum 0.00Preview
AVAX tokenAVAX 0.00Preview
Deposit · Ethereum → AvalancheNon-custodial bridge route
AVAX token AVAX
TypeBridge route
CustodyNon-custodial
Go to Swap
Scroll

Avalanche Bridge Protocol Architecture & Route Overview

Avalanche Bridge is Ava Labs' route for moving ETH and specifically listed Ethereum-origin ERC-20 tokens between Ethereum mainnet and Avalanche C-Chain.

Read more

In practice you open the bridge in Core, connect an externally owned wallet, pick Ethereum or C-Chain, review the quote, approve if needed, and sign; the flow and supported assets are described in the Avalanche Bridge support collection. Treat third-party dashboards such as DefiLlama's bridge view as independent context, not as a substitute for checking the live interface.

RouteEthereum mainnet <-> Avalanche C-Chain
DepositEthereum leg typically waits for 96 confirmations
WithdrawReturn unwraps and releases the Ethereum asset; do not resubmit
GasETH on Ethereum, AVAX on C-Chain
CustodyYour wallet signs; collateral sits under bridge architecture
VerifyUse the official interface; beware fake bridge sites
Avalanche Bridge

What is Avalanche Bridge?

Avalanche Bridge moves a defined set of Ethereum-origin assets between Ethereum and Avalanche C-Chain by locking or otherwise holding Ethereum collateral and representing it on Avalanche, usually with the .e suffix. It is not a DEX or a liquidity-routing aggregator; native USDC is the notable exception because it is handled through Circle CCTP rather than USDC.e wrapping.

A blockchain bridge creates a claim on another chain because an asset and its transaction history remain native to the source chain; it does not literally teleport the original token. This route is separate from Avalanche's internal X/P/C-Chain transfers and from Avalanche Interchain Messaging between Avalanche L1s.

How bridging works

Avalanche Bridge works by requesting an approval when the token requires one, then submitting the transfer transaction; the interface never receives your private keys. Bridge Nodes independently index the source chain, six of eight must agree, and the Intel SGX enclave signs the destination transaction, as described in the bridge architecture notes.

The same EVM address is used on both chains, so most users do not need a new address; they do need the right network selected and enough native gas on the side they are transacting from. Smart-contract wallets and direct sends to bridge contracts or wallets are unsupported.

Depositing to the destination

To deposit from Ethereum to C-Chain, connect the wallet, choose Ethereum as source and Avalanche C-Chain as destination, select a supported asset, and read the quoted fees before signing. The Ethereum leg typically waits for 96 confirmations, while the Avalanche leg usually completes within seconds.

Supported ERC-20 assets follow the ERC-20 token standard's approval-and-transfer pattern. Keep ETH for the source transaction and AVAX ready on C-Chain for whatever you plan to do next; arriving with a bridged token and zero AVAX leaves you unable to use the destination until you fund gas.

Withdrawing back

Withdrawing back to Ethereum is the unwrap path: the Avalanche representation is returned through the bridge process, and the Ethereum-origin asset is released to the same EVM address on mainnet.

Track the transfer by leg—Avalanche, Ethereum, or wallet network—because a slow first leg and a wallet displaying the wrong chain are different states.

Time and fees

Time and fees depend on the chain and asset: bridge fees are taken from the transferred asset, while source-chain gas is paid in ETH on Ethereum or AVAX on C-Chain. In the Ethereum gas model, gas pays for computation, so the all-in cost changes with network conditions and the asset you move rather than matching a fixed figure from an old screenshot.

Ethereum confirmation waiting dominates the deposit side, the C-Chain leg is usually quick, and a return transfer should be judged by which chain is finalizing at that moment.

Is Avalanche Bridge safe?

Avalanche Bridge has user-controlled wallet keys, SGX-gated signing, six-of-eight Bridge Node agreement before the destination transaction is signed, and a published Halborn audit. Those controls do not remove smart-contract, enclave, node, operational, approval, routing, or blockchain risk.

Before signing, verify the site, networks, token, approval scope, and destination address; use known support entry points, never share a seed phrase, and treat a page that requests an unlimited approval before showing the route or arrives via an ad or DM as untrusted until independently verified. L2BEAT's interoperability overview provides separate context for comparing cross-chain designs, but the transaction in your own wallet is the final check.

Problems and fixes

Most stalled transfers trace to a wrong network, no AVAX on arrival, an unsupported smart-contract wallet, a direct transfer to a bridge address, or a duplicate submission. Fix the network first, fund gas second, and then inspect the transfer status.

Avalanche-native tokens cannot be exported through this bridge, while Bitcoin bridging now uses separate Lombard infrastructure. A confirmed source transaction and a missing destination balance therefore require checking the relevant chain leg and asset representation, not sending a second transfer.

Verified Contract Gateway: 0x8453000000000000000000000000000000000000 (Chain verification active)

Avalanche FAQ

Is this the official Avalanche Bridge site?

No. This is an independent reference page; the live route, supported assets, and transaction details are determined by the official interface.

How long does bridging take?

The Ethereum leg typically waits for 96 confirmations, while the Avalanche C-Chain leg usually completes within seconds; the relevant wait is the chain leg still finalizing.

How do I bridge to Avalanche C-Chain?

Open the bridge in Core, connect a compatible externally owned wallet, select Ethereum to Avalanche C-Chain, choose a supported ETH or listed ERC-20 asset, review fees, approve if required, and sign the transfer. Keep ETH for source gas and AVAX for what you do after arrival.

Do I need AVAX before the bridged tokens arrive?

You need AVAX to use C-Chain after arrival because C-Chain gas is paid in AVAX. The bridge transfer itself is signed from the source side, so the token can arrive before you have the gas needed to swap, send, or withdraw further.

Is Avalanche Bridge safe?

It has meaningful controls: wallet keys stay with the user, SGX protects signing access, six-of-eight Bridge Nodes must agree, and a published Halborn audit exists. Those controls do not eliminate smart-contract, enclave, node, operational, approval, cross-chain, or phishing risk.

Is this a native route or a third-party swap route?

This bridge uses locked collateral and corresponding bridged tokens rather than DEX liquidity routing, with native USDC handled through Circle CCTP. It is distinct from Avalanche X/P/C-Chain transfers and from Avalanche Interchain Messaging between Avalanche L1s.

Notes before you use Avalanche Bridge

Practitioner note: the transfer is usually easy; the judgment is in route selection, approvals, and patience while finality does its job. The common mistake is sending tokens directly to a bridge contract or wallet instead of using the interface flow. Ethereum mainnet is chain ID 1, Avalanche C-Chain is chain ID 43114, source gas uses ETH, and C-Chain gas uses AVAX. Ethereum confirmations can dominate the wait, and a pending status is not a reason to duplicate the transaction. Verification: this page reflects public documentation and mechanism-level reasoning, not a live benchmark, last reviewed 21 July 2026. Independent reference — confirm the route in your own wallet.